Sharing events with structured metadata

ABSTRACT

When sharing events between users, the sharing users and the recipient users often have different relationships with details of the events. An event structurer enables sharing users to share events via a single user interface with recipients and tailor what aspects of the events are shared, thus ensuring the relevant portions of the events are properly presented to new recipients based on their new relationship with the event&#39;s details.

CROSS-REFERENCE TO RELATED APPLICATION PAPERS

This application is a continuation of U.S. application Ser. No.15/588,273, filed May 5, 2017, and which application is incorporatedherein by reference in its entirety. A claim of priority is made to theabove disclosed application.

BACKGROUND

Users of email and calendaring applications often share messages thatthey have received by forwarding those messages to a new recipient.Similarly, new attendees can be invited or assigned action items relatedto an existing calendar event by forwarding an invitation. As emailsystems have gained sophistication, one service offered to users is theability to parse incoming messages to identify relevant event metadatawithin the message and automatically create events in the user'scalendar based on those event metadata. When messages or calendar eventsare forwarded, these event metadata may have different relevancy for thenew recipient/invitee than the sharing user, which causes difficultiesin the automatic provision and parsing of the metadata.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription section. This summary is not intended to identify all key oressential features of the claimed subject matter, nor is it intended asan aid in determining the scope of the claimed subject matter.

Systems, methods, and computer readable storage devices embodyingprocessor executable instructions for sharing events with structuredmetadata are provided herein. In one aspect, an email message isreceived from a source and is parsed to identify any event metadata itcontains from which an event is automatically created for the originalrecipient. In another aspect, details from an existing event areselected for use as event metadata. The sharing user selects newrecipients and roles for those new recipients via a user interfaceintegrated into a mail and/or calendar application. Selected eventmetadata, and their relationship to the new recipients, are integratedinto an email message, which is then shared to the new recipients. Thenew recipients are provided the event metadata—originally relevant tothe sharing user—in a context relevant to the new recipients. In variousaspects, receiving users configure whether calendar events areautomatically created upon receipt or may be created in response to useracknowledgement/acceptance of the shared event metadata.

By sharing events with structured metadata as described in the presentdisclosure, increases in computational efficiency and reductions inbandwidth usage are realized, while an improved user experience (forboth sharing and new receiving users) is provided. Users are therebyprovided tools to efficiently and easily share events with one anotherthat require less data to be transmitted between mail and calendarservers with greater fidelity to the event's meaning to the individualusers.

Examples are implemented as a computer process, a computing system, oras an article of manufacture such as a device, computer program product,or computer readable medium. According to an aspect, the computerprogram product is a computer storage medium readable by a computersystem and encoding a computer program comprising instructions forexecuting a computer process.

The details of one or more aspects are set forth in the accompanyingdrawings and description below. Other features and advantages will beapparent from a reading of the following detailed description and areview of the associated drawings. It is to be understood that thefollowing detailed description is explanatory only and is notrestrictive of the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this disclosure, illustrate various aspects. In the drawings:

FIG. 1 is an example operating environment in which the presentdisclosure may be practiced;

FIGS. 2A-G are example user interfaces in which an example event isshared with structured metadata;

FIG. 3 is a flow chart showing general stages involved in an examplemethod for sharing events with structured metadata;

FIG. 4 is a block diagram illustrating example physical components of acomputing device;

FIGS. 5A and 5B are block diagrams of a mobile computing device; and

FIG. 6 is a block diagram of a distributed computing system.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description refers to the same or similar elements.While examples may be described, modifications, adaptations, and otherimplementations are possible. For example, substitutions, additions, ormodifications may be made to the elements illustrated in the drawings,and the methods described herein may be modified by substituting,reordering, or adding stages to the disclosed methods. Accordingly, thefollowing detailed description is not limiting, but instead, the properscope is defined by the appended claims. Examples may take the form of ahardware implementation, or an entirely software implementation, or animplementation combining software and hardware aspects. The followingdetailed description is, therefore, not to be taken in a limiting sense.

FIG. 1 illustrates and example operating environment 100 in which thepresent disclosure may be practiced. As illustrated, a sender device110, associated with a sender (also referred to as an originalrecipient, a sharing user, a sharer, and variations thereof), shares anevent with one or more receiver devices 120, associated with one or morenew recipients (also referred to as receivers, invitees, and variationsthereof). In various aspects, the event that is shared originated froman email sent from event originator 130 or a user-created eventoriginating from the sender device 110. A sender email server 140including an event structurer 150 is in communication with the senderdevice 110, the event originator 130, a receiver email server 160, andan enrichment database 170. In some aspects, the sender email server 140and the receiver email server 160 are the same email server. Inadditional aspects, the enrichment database 170 is a component of thesender email server 140 or an externally maintained database.

The sender device 110, receiver device 120, event originator 130, senderemail server 140, event structurer 150, receiver email server 160, andenrichment database 170 are illustrative of a multitude of computingsystems including, without limitation, desktop computer systems, wiredand wireless computing systems, mobile computing systems (e.g., mobiletelephones, netbooks, tablet or slate type computers, notebookcomputers, and laptop computers), hand-held devices, multiprocessorsystems, microprocessor-based or programmable consumer electronics,minicomputers, printers, and mainframe computers. The hardware of thesecomputing systems is discussed in greater detail in regard to FIGS. 4-6.

While the sender device 110, receiver device 120, event originator 130,sender email server 140, event structurer 150, receiver email server160, and enrichment database 170 are shown remotely from one another forillustrative purposes, it should be noted that several configurations ofone or more of these devices hosted locally to another illustrateddevice are possible, and each illustrated device may represent multipleinstances of that device. Various servers and intermediaries familiar tothose of ordinary skill in the art may lie between the component systemsillustrated in FIG. 1 to route the communications between those systems,which are not illustrated so as not to distract from the novel aspectsof the present disclosure.

The sender device 110 and the receiver device 120 provide email andcalendaring applications for their respective users. In various aspects,these applications provide email and calendaring functions via separateapplications (e.g., a first application providing email functionality, asecond application providing calendaring functionality) or viaintegrated applications (e.g., an email and calendaring application).The devices are operable to provide one or more calendaring applicationsassociated with various accounts or profiles for their users, such as,for example, a user may access work email and events via the IBM NOTES®enterprise email client (provided by International Business Machines,Corp. of Armonk, N.Y.) and on the same device access personal email andevents via the GMAIL® online email and calendar platform (provided byAlphabet, Inc. of Mountain View, Calif.). The email and calendarapplications provided by the sender device 110 and the receiver device120 include both thick clients (running on the device) and thin clients(running on a remote server and accessed via a web browser), and thesender device 110 and the receiver device 120 do not need to run oraccess the same email and calendaring applications; each device isoperable to use different applications to practice the presentdisclosure.

The sender email server 140 and the receiver email server 160 provideemail and calendar event management for multiple users, including thesender and the recipient. In some aspects, such as when the sender andthe recipient are coworkers, the sender email server 140 and thereceiver email server 160 are the same device or distributed network ofdevices (e.g., different physical devices within a cloud computingenvironment managed as one entity). In other aspects, the sender emailserver 140 and the receiver email server 160 are different devices thatrun the same or different applications to manage the provision of emailand calendar events to the users. In one example, a sender email server140 running SENDMAIL® (provided by Sendmail, Inc. of Emeryville, Calif.)is in communication with a receiver email server 160 running EXIM™(provided at www.exim.org).

The event structurer 150 is configured to parse emails received fordistribution to its users and determine whether any event metadata ispresent in the emails and, if so, to provide the event metadata in adigested format. For example, when an email containing hotel reservationdetails is received from an event originator 130 of a hotel or travelagent, the event structurer 150 is operable to locate details regardingthe hotel stay in the email and break those details out in an easilydigested format for the user to read and interact with. In anotherexample, when an email containing package delivery details is receivedfrom an event originator 130 of a retailer or delivery service, theevent structurer 150 is operable to locate details regarding the time ofdelivery and location of the package and provide those details to theuser to read and interact with in an easily digestible format. Thedigestible format includes structured arrangements of data elements,infographics, hyperlinks to relevant third party websites (e.g., acheck-in website for a flight, a package tracker website, a customersupport website), and the like, which can be configured by the user invarious aspects. Although only illustrated in conjunction with thesender email server 140, one of ordinary skill in the art willappreciate that the receiver email server 160 will also incorporate anevent structurer 150 in some aspects, but that such incorporation isoptional.

To parse the emails for event metadata, the event structurer 150 isconfigured to use the schema.org or another structured data vocabularyto identify terms within an email message and to develop a structure ofthat information for inclusion in the message delivered to the senderdevice 110. In various aspects, such as when the email message isformatted as an HTML (Hypertext Markup Language) object, the structuredmetadata are included in the body field as metadata as a division withinthe body field. The structured division is provided in a machinereadable format for the email and calendaring client to interpret andmay be hidden from the user or presented to the user as the easilydigestible format depending on whether the email and calendaring clientis configured to interpret the structured division. For example, if auser accesses the parsed email via two different clients—one enabled tointerpret the structured division and one not—the user will still seethe message body of the email in both clients, but only the enabledclient will provide the additional functionality of the easilydigestible format.

In various aspects, the parsed email is identified as being related toan event, and the extracted data are used by the event structurer 150 toautomatically produce a calendar event for the user. For example, anemail including data for a flight reservation is parsed, and such dataare included in the structure of the email to provide an eventcorresponding to the flight and travel times for the user. In anotherexample, an email including data for a concert is parsed, and such dataare included in the structure of the email to provide an eventcorresponding to the concert's duration and location (e.g., from 6 pmuntil 10 pm at the Wiener Staatsoper, Opernring 2). These events areautomatically added to the user's calendar or provided to the user toaccept as an event invitation message depending on user preferences.

Additionally, based on the extracted metadata from the emails,additional data based on those extracted data are located by the eventstructurer 150 via an enrichment database 170. For example, if theextracted data include an airport code, a postal code, time zoneinformation, or the like, the data to convert the extracted informationwill be provided for the airport name or location (e.g., TYS→McGee Tysonin Knoxville, Tenn.), associated city or state (e.g., 90210→BeverlyHills, Calif. or greater Los Angeles area), or localized timeinformation (e.g., 2000 NPT→8:00 pm Nepal Standard Time [UTC+5:45] or10:15 am EDT). The enrichment database 170 provides various conversionsfor coded information as well as synonyms, translations, and expandedinformation (e.g., maps of an identified location, whether a holiday isassociated with a time/location) that the event structurer 150 canincorporate into the structured message for provision in the easilydigestible format and/or the event.

Event metadata include, but are not limited to: a subject matter,actors/presenters, ratings, attendees, intended audiences, composers,contributors, door times, durations, start/end times, status (e.g., ontime, rescheduled, cancelled), language, whether sub/super events exist,descriptions, Uniform Resource Locators (URLs) to access the event orrelated website, an event type, etc. The event metadata are stored atthe sender email server 140 along with the message from which they wereparsed so that when a sharing user forwards or shares a message or eventwith a recipient user, those metadata are included in the sharingmessage and formatted according to their (different) relationship to therecipient user.

In the course of operation, the sender device 110 will receive emailsand calendar events (e.g., invitations) from the sender email server 140from various sources that have been parsed by the event structurer 150for event metadata. These event metadata have been parsed from theoriginal message based on their relationship with the user to whom theoriginal message was addressed. For example, the flight times from aflight confirmation message are related to when the user is expected tofly from an origin to a destination. The user, however, may wish toshare this information with various other persons who are not ticketedfor the flight outlined in the original message, such as, for example, aperson who will pick up or drop off the user from/to an airport. Theseother persons with whom the user shares the message will have adifferent relationship with the event metadata than the user, and whenthe user shares the event with these persons, the event structurer 150provides these other persons (e.g., recipient users) the metadata inaccord with the new relationship.

The metadata encoded in the event message by the sending user forvarious recipients may include all or a portion of the metadata parsedby the event structurer 150 or, when the event was manually created, allor a portion of the metadata for the event may be determined andinjected into the event message to be shared with the recipients.Similar to the example message received from the event originator 130discussed above, the event message encodes the metadata related to therecipients in a machine-readable division of the HTML body of the eventmessage, and designates (e.g., via a field name or value) that the eventmessage is a shared event. The new relationships of the event to therecipients, and the metadata associated with those relationships, areset by the sending user via an interface in the sender's email andcalendaring application. An example course of operations and associatedexample user interfaces (UIs) therefor are illustrated in FIGS. 2A-G.

FIG. 2A illustrates a sender email UI 210 in which an email message fora flight is provided with expanded functionality based on the structureddata originally present in the message from the event originator 130.Various navigation controls are provided in the sender email UI 210 toenable the sending user to view, delete, and manipulate email messagesand event invitations. A message viewing pane 220 is provided to viewdetails about a selected email message, providing transmissioninformation 221, a message body 222, and structured event data 223. Invarious aspects, the data used to construct the structured event data223 are parsed from the original message and provided in a machinereadable division of the message body. The email client is operable touse the division within the body and provide the associated metadata tothe use via various infographics, images, arrangements, and hyperlinksor other controls in an easily digested format. The format shown in FIG.2A is provided as a non-limiting example, and other arrangements andformats are possible.

FIG. 2B illustrates a calendar client UI 230 in which the event parsedfrom the example message from FIG. 2A is provided. Various controls areprovided in the calendar client UI 230 to enable to user to interactwith the event, such as reminder controls, controls to view theassociated email, controls to access links parsed from the emails whenavailable (e.g., the “check in” hyperlink is disabled until the user cancheck in, typically 24-hours before a flight is scheduled to depart),and information about the event based on the metadata parsed from theoriginal message. One control included in the calendar client UI 230 isa share control 231, which enables the user to format a new message toshare the event with additional persons. In various aspects, the sharecontrol 231 is bi-actuable, enabling a user to actuate the share control231 in one of two way to provide two distinct functionalities (e.g.,left-click for a first functionality, right-click for a secondfunctionality). In other aspects, two separate controls are provided asthe share control 231 to provide each of the functionalities.

FIG. 2C illustrates a first functionality provided in response toactuating the share control 231, in which a user is provided a sharingUI 240 by which to share the event with one or more recipients. Thesharing UI 240 includes controls to title the event, identify recipientswith whom to share the event, include a message with the event, send theevent, and to cancel sending the event. Although shown as a pop-upwindow, the sharing UI 240 also includes new windows and new frames inexisting windows in other aspects.

As illustrated, the user has selected to share the calendar event thatwas created from the metadata extracted from an email received fromFreedonia Airlines for a flight to Los Angeles. As will be appreciated,a user may share various events based on metadata parsed from receivedemails (e.g., hotel reservations, concert tickets, package tracking),existing calendar items, as well as events that were manually created bythe user.

FIG. 2D illustrates the sharing UI 240 in which the user has filled outthe several fields, updating the title, identifying two recipients, andadding a message. As illustrated, the user (John Doe) has titled themessage to be shared “John's Flight to Los Angeles” instead of theoriginal event's subject, has addressed the message to be shared withtwo recipients (Erika Mustermann and Ivan Ivanovich), and has included amessage to provide details to why the event is being shared. In variousaspects, the sharing UI 240 includes more or fewer controls and indifferent arrangements than those illustrated herein.

FIG. 2E illustrates a second functionality provided in response toactuating the share control 231, in which a user is provided an optionsmenu 250. The options menu 250 is populated with various controls toenable the sending user to select what metadata are shared with therecipients and how the recipients are shared those metadata. In oneexample, the parsed metadata from the message are provided as optionsthat the user is enabled to select from to share with variousrecipients.

As illustrated, John has selected to share “Provider Information”,“Start Time”, and “End Time” with Erika and Ivan, but has opted not toprovide the original message, so that Erika and Ivan will know whichairline John is flying with and when, but do not need to be providedwith all of John's flight details and will not be provided with theoriginal message, thus focusing the metadata to that (potentially)related to the recipients and thereby reducing the data needed to betransmitted. In another example, if John were asking a differentrecipient (e.g., Jane Doe) for a ride to the airport, John would be ableto exclude the Original Message and the End Time from the message toJane, who only needs to know when and where John needs to be at theairport he is departing from and not about when he is arriving at hisdestination. In this example, metadata are excluded from the message toJane that are extraneous to her potential relationship with the event,thus reducing the amount of data needed to be transmitted to Jane.

In further aspects, the format of the shared message is altered from theoriginal message or event, which enables further improvements inreadability and security as well as reductions in data needed to betransmitted to share events. In a first example, the email received byJohn from Freedonia Airlines that includes a logo image for FreedoniaAirlines, a tokenized link for John to login and access his frequentflier account, and special offers from the airline (or its partners) arestripped from the original message when creating a shared message. Thus,distractions, irrelevant information, personalized information, and thelike are removed and do not need to be transmitted when sharing theevent with the recipients. The removal of these extraneous data isperformed (according user preferences) when sharing events as describedherein through a sharing UI 240, but also automatically when forwardingemail messages and calendar items. As will also be appreciated, thesharing user is enabled to change the order in which information ispresented to the recipients from that originally presented in theoriginal message or event to further enhance the readability of theshared message.

Although four options are shown in the options menu in FIG. 2E relatedto the original message and its metadata, a more options control enablesthe user to interact with options that are not initially shown, and itwill be appreciated that more or fewer options are provided in differentaspects. In various aspects, a more options control provides a newwindow (modal or non-modal), a dropdown or expansion of the options menu250, or repopulates the options menu 250 with different options.

In various aspects, sharing users are provided templates to selectpre-selected portions or sets of the metadata to share with recipients.The templates that the user is enabled to select from include systemdefined and user defined templates to speed the selection of metadata toinclude in the shared message. In some aspects, based on the contents ofthe text entered for the shared message, the email client or eventstructure 150 is operable to automatically apply a template or tosuggest one or more templates to the user if the user has not selectedone when attempting to send the shared message.

FIG. 2F illustrates a recipient email UI 260 in which the shared eventmessage is displayed with all of the metadata for the shared event.Similar to the sender email UI 210, the recipient email UI 260 includesa message viewing pane 220 for a selected email message that includestransmission information 221, a message body 222, and structured eventdata 223. Additionally, based on the division encoding the shared eventdata, the message viewing pane 220 for the recipient email UI 260includes a sharing notification 224 for the event, indicating that theevent has been shared from the sharing user and including additionaldetails on the event and/or initiating email (e.g., attaching the email)and a calendar control 225 to enable the recipient users to add theshared event to their personal calendar. In various aspects, the sharedevent is not automatically added to the recipient's calendar uponreceipt of the event message, but requires the user to actuate thecalendar control 225 to accept the shared event onto the recipient'spersonal calendar. In other aspects, the recipient's user preferencesautomatically accept shared events from designated sharing users. In yetother aspects, when the shared event is part of the recipient'scalendar, the calendar control 225 is actuable to enable the recipientuser to remove the shared event from the recipient's calendar.

FIG. 2G illustrates a recipient email UI 260 in which the shared eventmessage is displayed with a portion of the metadata for the sharedevent. In various aspects, the sending user selects for a portion of themetadata unrelated to the recipient's potential relationship to theevent to be omitted from the sharing message. Similar to the layoutillustrated in FIG. 2F, the recipient email UI 260 includes transmissioninformation 221, a message body 222, and structured event data 223,sharing notification 224, and calendar control 225, but the datapresented in the structured event data 223 section reflects the subsetof the metadata presented to the recipient user. For example, instead ofshowing all of the flight details for John that Erika and Ivan would seein FIG. 2F if John shared all of the flight information in the sharingmessage, Jane would see drop-off details as are illustrated in FIG. 2Gif John just shared his departure details.

An event structurer 150 (either at the sender email server 140 or thereceiver email server 160) is operable to consult an enrichment database170 to provide additional data for populating the segment for structuredevent data 223 in the recipient email UI 260 according to the metadatashared with the particular recipient. In the illustrated example of FIG.2F, Erika and Ivan, who were provided all of John's flight details, areshown additional details related to the flight event augmented from theincluded metadata (origin and destination cities, durations, etc.). Inthe illustrated example of FIG. 2G, Jane, who was provided detailsrelated to John's departure, and not provided details of John's arrivalin Los Angeles, is shown additional details related to the departurepoint (SEA-TAC airport) pertinent to her relationship with the event.

FIG. 3 is a flow chart showing general stages involved in an examplemethod 300 for sharing events with structured metadata. Method 300begins with OPERATION 305, where a message detailing an event (such asan email for a flight, hotel, car rental, package delivery, concert,conference, etc.) is received for a user at a server. Method 300proceeds to OPERATION 310, where the message is parsed for metadatarelated to the event. For example, an event structurer 150 parses themessage for key terms and known arrangements of terms related to eventdetails. The key terms and known arrangements are defined in variousschema and vocabulary lists, including those defined in the schema.orgor other structured data vocabularies and those defined manually by theuser or automatically (e.g., by a machine learning analysis of emailsand calendar item) by the event structurer 150.

Method 300 optionally proceeds to OPERATION 315 to enrich the parsedmetadata from the message with additional or substitute data. The dataused to enrich the extracted metadata are identified in an enrichmentdatabase 170 and are used to provide additional details of the event tothe user. In one example, expansions of known abbreviations or codes inthe event metadata are added to the message. In a second example, mapsfor identified locations in the metadata are identified and included inthe message. In a third example, infographics are developed based on themetadata and included in the message (e.g., a shipment or flighttracker). In a fourth example, when a person related to the event isidentified in the event metadata (e.g., a performer, director,presenter, etc.), a biography of that person is identified in theenrichment database 170 and included in the message (e.g., as ahyperlink to a profile webpage for that person).

At OPERATION 320 metadata parsed from the message is stored inassociation with the message. In various aspects, the parsed metadataare stored in a machine readable division of the body of the message,while in other aspects the parsed metadata are stored in a separatefiled linked to the message. Method 300 then proceeds to OPERATION 325,where a calendar item for the event is created for the user based on theparsed metadata. For example, when start and end times are parsed from amessage, the calendar item will use those times to define the event inthe user's electronic calendar. In other aspects, additional metadatapulled for specific fields are used to title and include details aboutthe event for use in the calendar item. The parsed metadata areassociated with the calendar item, either as part of the data definingthe calendar item or as a linked reference to an external file.

The user is given access to the message and the calendar item atOPERATION 330. In various aspects, depending on the user's preferencesfor their email and calendaring applications and the settings of theuser's email server, the message and content item are downloaded to theuser's device and deleted from the email server, the message and contentitem are downloaded to the user's device and remain available from theemail server, or are accessed at the email server via the user's device.

Proceeding to OPERATION 335, a user share action is received. In variousaspects, the user share action originates from an email application or acalendar application (or a given email/calendar functionality of acombined email and calendar application), and references an existingcalendar item or an email containing event information that has not yetbeen added as a calendar item. The user share action identifies acalendar item and some or all of the metadata related to the eventrepresented by the calendar item to share with one or more recipientusers identified by the sharing user. A shared message is created inresponse to the share action at OPERATION 340, which includes theuser-specified metadata, which are embedded in a machine readabledivision of the shared message body for sharing the event to therecipients. In several aspects, the shared message is an HTML emailmessage, which optionally includes a title and a sending-user-definedmessage for the recipient users, and/or the original message or calendaritem as an attachment. In other aspects, such as when optional OPERATION345 is performed, the shared message is a shared calendar item (such asan event invitation or assignment) that is destined for the recipientuser's electronic calendar.

The metadata are organized according to a format readable by thereceiver email server 160, such as, for example, the Schema.org format,and may include all or less than all of the metadata that the originalmessage (or calendar item) contains. Additionally, the metadata may beaugmented from those parsed from the original message with enrichmentdata related to the metadata, including, but not limited to: a map for avenue or location related to the event, a hyperlink to a website for anevent originator 130 or venue/location of the event, a full name of anentity described in the message by a code, etc.

The shared message is transmitted to the recipient user at OPERATION350. Once the recipient has accessed the shared message via theassociated receiver email server 160, the receiver email server 160will, depending on its setup and the receiver user's preferences and theabilities of the receiver user's email and calendaring client, providethe recipient with the shared message and optionally create an event forthe recipient or provide a control associated with the shared message toadd the event to the recipient's calendar.

While implementations have been described in the general context ofprogram modules that execute in conjunction with an application programthat runs on an operating system on a computer, those skilled in the artwill recognize that aspects may also be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, and other types of structuresthat perform particular tasks or implement particular abstract datatypes.

The aspects and functionalities described herein may operate via amultitude of computing systems including, without limitation, desktopcomputer systems, wired and wireless computing systems, mobile computingsystems (e.g., mobile telephones, netbooks, tablet or slate typecomputers, notebook computers, and laptop computers), hand-held devices,multiprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, and mainframe computers.

In addition, according to an aspect, the aspects and functionalitiesdescribed herein operate over distributed systems (e.g., cloud-basedcomputing systems), where application functionality, memory, datastorage and retrieval and various processing functions are operatedremotely from each other over a distributed computing network, such asthe Internet or an intranet. According to an aspect, user interfaces andinformation of various types are displayed via on-board computing devicedisplays or via remote display units associated with one or morecomputing devices. For example, user interfaces and information ofvarious types are displayed and interacted with on a wall surface ontowhich user interfaces and information of various types are projected.Interaction with the multitude of computing systems with whichimplementations are practiced include, keystroke entry, touch screenentry, voice or other audio entry, gesture entry where an associatedcomputing device is equipped with detection (e.g., camera) functionalityfor capturing and interpreting user gestures for controlling thefunctionality of the computing device, and the like.

FIGS. 4-6 and the associated descriptions provide a discussion of avariety of operating environments in which examples are practiced.However, the devices and systems illustrated and discussed with respectto FIGS. 4-6 are for purposes of example and illustration and are notlimiting of a vast number of computing device configurations that areused for practicing aspects, described herein.

FIG. 4 is a block diagram illustrating physical components (i.e.,hardware) of a computing device 400 with which examples of the presentdisclosure may be practiced. In a basic configuration, the computingdevice 400 includes at least one processing unit 402 and a system memory404. According to an aspect, depending on the configuration and type ofcomputing device, the system memory 404 comprises, but is not limitedto, volatile storage (e.g., random access memory), non-volatile storage(e.g., read-only memory), flash memory, or any combination of suchmemories. According to an aspect, the system memory 404 includes anoperating system 405 and one or more program modules 406 suitable forrunning software applications 450. According to an aspect, the systemmemory 404 includes event structurer 150. The operating system 405, forexample, is suitable for controlling the operation of the computingdevice 400. Furthermore, aspects are practiced in conjunction with agraphics library, other operating systems, or any other applicationprogram, and are not limited to any particular application or system.This basic configuration is illustrated in FIG. 4 by those componentswithin a dashed line 408. According to an aspect, the computing device400 has additional features or functionality. For example, according toan aspect, the computing device 400 includes additional data storagedevices (removable and/or non-removable) such as, for example, magneticdisks, optical disks, or tape. Such additional storage is illustrated inFIG. 4 by a removable storage device 409 and a non-removable storagedevice 410.

As stated above, according to an aspect, a number of program modules anddata files are stored in the system memory 404. While executing on theprocessing unit 402, the program modules 406 (e.g., event structurer150) perform processes including, but not limited to, one or more of thestages of the method 300 illustrated in FIG. 3. According to an aspect,other program modules are used in accordance with examples and includeapplications such as electronic mail and contacts applications, wordprocessing applications, spreadsheet applications, databaseapplications, slide presentation applications, drawing or computer-aidedapplication programs, etc.

According to an aspect, the computing device 400 has one or more inputdevice(s) 412 such as a keyboard, a mouse, a pen, a sound input device,a touch input device, etc. The output device(s) 414 such as a display,speakers, a printer, etc. are also included according to an aspect. Theaforementioned devices are examples and others may be used. According toan aspect, the computing device 400 includes one or more communicationconnections 416 allowing communications with other computing devices418. Examples of suitable communication connections 416 include, but arenot limited to, radio frequency (RF) transmitter, receiver, and/ortransceiver circuitry; universal serial bus (USB), parallel, and/orserial ports.

The term computer readable media, as used herein, includes computerstorage media. Computer storage media include volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information, such as computer readableinstructions, data structures, or program modules. The system memory404, the removable storage device 409, and the non-removable storagedevice 410 are all computer storage media examples (i.e., memorystorage.) According to an aspect, computer storage media include RAM,ROM, electrically erasable programmable read-only memory (EEPROM), flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other article ofmanufacture which can be used to store information and which can beaccessed by the computing device 400. According to an aspect, any suchcomputer storage media are part of the computing device 400. Computerstorage media do not include a carrier wave or other propagated datasignal.

According to an aspect, communication media are embodied by computerreadable instructions, data structures, program modules, or other datain a modulated data signal, such as a carrier wave or other transportmechanism, and include any information delivery media. According to anaspect, the term “modulated data signal” describes a signal that has oneor more characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media include wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, radiofrequency (RF), infrared, and other wireless media.

FIGS. 5A and 5B illustrate a mobile computing device 500, for example, amobile telephone, a smart phone, a tablet personal computer, a laptopcomputer, and the like, with which aspects may be practiced. Withreference to FIG. 5A, an example of a mobile computing device 500 forimplementing the aspects is illustrated. In a basic configuration, themobile computing device 500 is a handheld computer having both inputelements and output elements. The mobile computing device 500 typicallyincludes a display 505 and one or more input buttons 510 that allow theuser to enter information into the mobile computing device 500.According to an aspect, the display 505 of the mobile computing device500 functions as an input device (e.g., a touch screen display). Ifincluded, an optional side input element 515 allows further user input.According to an aspect, the side input element 515 is a rotary switch, abutton, or any other type of manual input element. In alternativeexamples, mobile computing device 500 incorporates more or fewer inputelements. For example, the display 505 may not be a touch screen in someexamples. In alternative examples, the mobile computing device 500 is aportable phone system, such as a cellular phone. According to an aspect,the mobile computing device 500 includes an optional keypad 535.According to an aspect, the optional keypad 535 is a physical keypad.According to another aspect, the optional keypad 535 is a “soft” keypadgenerated on the touch screen display. In various aspects, the outputelements include the display 505 for showing a graphical user interface(GUI), a visual indicator 520 (e.g., a light emitting diode), and/or anaudio transducer 525 (e.g., a speaker). In some examples, the mobilecomputing device 500 incorporates a vibration transducer for providingthe user with tactile feedback. In yet another example, the mobilecomputing device 500 incorporates input and/or output ports, such as anaudio input (e.g., a microphone jack), an audio output (e.g., aheadphone jack), and a video output (e.g., a HDMI port) for sendingsignals to or receiving signals from an external device. In yet anotherexample, the mobile computing device 500 incorporates peripheral deviceport 540, such as an audio input (e.g., a microphone jack), an audiooutput (e.g., a headphone jack), and a video output (e.g., a HDMI port)for sending signals to or receiving signals from an external device.

FIG. 5B is a block diagram illustrating the architecture of one exampleof a mobile computing device. That is, the mobile computing device 500incorporates a system (i.e., an architecture) 502 to implement someexamples. In one example, the system 502 is implemented as a “smartphone” capable of running one or more applications (e.g., browser,e-mail, calendaring, contact managers, messaging clients, games, andmedia clients/players). In some examples, the system 502 is integratedas a computing device, such as an integrated personal digital assistant(PDA) and wireless phone.

According to an aspect, one or more application programs 550 are loadedinto the memory 562 and run on or in association with the operatingsystem 564. Examples of the application programs include phone dialerprograms, e-mail programs, personal information management (PIM)programs, word processing programs, spreadsheet programs, Internetbrowser programs, messaging programs, and so forth. The system 502 alsoincludes a non-volatile storage area 568 within the memory 562. Thenon-volatile storage area 568 is used to store persistent informationthat should not be lost if the system 502 is powered down. Theapplication programs 550 may use and store information in thenon-volatile storage area 568, such as e-mail or other messages used byan e-mail application, and the like. A synchronization application (notshown) also resides on the system 502 and is programmed to interact witha corresponding synchronization application resident on a host computerto keep the information stored in the non-volatile storage area 568synchronized with corresponding information stored at the host computer.As should be appreciated, other applications may be loaded into thememory 562 and run on the mobile computing device 500.

According to an aspect, the system 502 has a power supply 570, which isimplemented as one or more batteries. According to an aspect, the powersupply 570 further includes an external power source, such as an ACadapter or a powered docking cradle that supplements or recharges thebatteries.

According to an aspect, the system 502 includes a radio 572 thatperforms the function of transmitting and receiving radio frequencycommunications. The radio 572 facilitates wireless connectivity betweenthe system 502 and the “outside world,” via a communications carrier orservice provider. Transmissions to and from the radio 572 are conductedunder control of the operating system 564. In other words,communications received by the radio 572 may be disseminated to theapplication programs 550 via the operating system 564, and vice versa.

According to an aspect, the visual indicator 520 is used to providevisual notifications and/or an audio interface 574 is used for producingaudible notifications via the audio transducer 525. In the illustratedexample, the visual indicator 520 is a light emitting diode (LED) andthe audio transducer 525 is a speaker. These devices may be directlycoupled to the power supply 570 so that when activated, they remain onfor a duration dictated by the notification mechanism even though theprocessor 560 and other components might shut down for conservingbattery power. The LED may be programmed to remain on indefinitely untilthe user takes action to indicate the powered-on status of the device.The audio interface 574 is used to provide audible signals to andreceive audible signals from the user. For example, in addition to beingcoupled to the audio transducer 525, the audio interface 574 may also becoupled to a microphone to receive audible input, such as to facilitatea telephone conversation. According to an aspect, the system 502 furtherincludes a video interface 576 that enables an operation of an on-boardcamera 530 to record still images, video stream, and the like.

According to an aspect, a mobile computing device 500 implementing thesystem 502 has additional features or functionality. For example, themobile computing device 500 includes additional data storage devices(removable and/or non-removable) such as, magnetic disks, optical disks,or tape. Such additional storage is illustrated in FIG. 5B by thenon-volatile storage area 568.

According to an aspect, data/information generated or captured by themobile computing device 500 and stored via the system 502 are storedlocally on the mobile computing device 500, as described above.According to another aspect, the data are stored on any number ofstorage media that are accessible by the device via the radio 572 or viaa wired connection between the mobile computing device 500 and aseparate computing device associated with the mobile computing device500, for example, a server computer in a distributed computing network,such as the Internet. As should be appreciated such data/information areaccessible via the mobile computing device 500 via the radio 572 or viaa distributed computing network. Similarly, according to an aspect, suchdata/information are readily transferred between computing devices forstorage and use according to well-known data/information transfer andstorage means, including electronic mail and collaborativedata/information sharing systems.

FIG. 6 illustrates one example of the architecture of a system forsharing events with structured metadata as described above. Contentdeveloped, interacted with, or edited in association with the eventstructurer 150 is enabled to be stored in different communicationchannels or other storage types. For example, various documents may bestored using a directory service 622, a web portal 624, a mailboxservice 626, an instant messaging store 628, or a social networking site630. The event structurer 150 is operative to use any of these types ofsystems or the like for sharing events with structured metadata, asdescribed herein. According to an aspect, a server 620 provides theevent structurer 150 to clients 605 a,b,c. As one example, the server620 is a web server providing the event structurer 150 over the web. Theserver 620 provides the event structurer 150 over the web to clients 605through a network 640. By way of example, the client computing device isimplemented and embodied in a personal computer 605 a, a tabletcomputing device 605 b or a mobile computing device 605 c (e.g., a smartphone), or other computing device. Any of these examples of the clientcomputing device are operable to obtain content from the store 616.

Implementations, for example, are described above with reference toblock diagrams and/or operational illustrations of methods, systems, andcomputer program products according to aspects. The functions/acts notedin the blocks may occur out of the order as shown in any flowchart. Forexample, two blocks shown in succession may in fact be executedsubstantially concurrently or the blocks may sometimes be executed inthe reverse order, depending upon the functionality/acts involved.

The description and illustration of one or more examples provided inthis application are not intended to limit or restrict the scope asclaimed in any way. The aspects, examples, and details provided in thisapplication are considered sufficient to convey possession and enableothers to make and use the best mode. Implementations should not beconstrued as being limited to any aspect, example, or detail provided inthis application. Regardless of whether shown and described incombination or separately, the various features (both structural andmethodological) are intended to be selectively included or omitted toproduce an example with a particular set of features. Having beenprovided with the description and illustration of the presentapplication, one skilled in the art may envision variations,modifications, and alternate examples falling within the spirit of thebroader aspects of the general inventive concept embodied in thisapplication that do not depart from the broader scope.

We claim:
 1. A system for sharing events with structured metadatacomprising: a processor; a memory storage device including instructionsthat when executed by the processor provide an event structurerconfigured to: receive a message transmitted from a sender to anoriginal recipient that is related to an event for the originalrecipient; parse the message to identify metadata of the event; create acalendar item for the original recipient based on the metadata; receive,from the original recipient, a share action identifying a new recipient;receive, from the original recipient, a selection of a portion of themetadata relevant to the new recipient; incorporate the selected portionof the metadata relevant to the new recipient into a shared message; andcause transmission of the shared message to the new recipient.
 2. Thesystem of claim 1, wherein the shared message is a calendar eventinvitation.
 3. The system of claim 1, wherein the metadata areincorporated into the shared message as a machine-readable division ofan HTML (Hypertext Markup Language) body section of an email.
 4. Thesystem of claim 1, wherein the event structurer is further configuredto: identify enrichment data in an enrichment database related to themetadata parsed from the message; and insert the enrichment data intothe shared message to enrich the metadata.
 5. The system of claim 4,wherein the enrichment data include at least one of: a map; a hyperlinkto a website; and a full name of an entity described in the message by acode.
 6. The system of claim 1, wherein the selection of a portion ofthe metadata relevant to the new recipient is received as a selection ofa user interface element from a displayed menu.
 7. A method for sharingevents with structured metadata comprising: receiving an emailtransmitted from a sender to an original recipient; parsing the email toidentify metadata associated with an event related to the originalrecipient; creating a calendar item for the original recipient based onthe event; receiving, from the original recipient, a share actionidentifying a new recipient; receiving, from the original recipient, aselection of a portion of the metadata relevant to the new recipient;creating a shared message, the shared message including the portion ofthe metadata relevant to the new recipient and an indicator that theshared message is a shared event; and transmitting the shared message tothe new recipient.
 8. The method of claim 7, further comprising causinga display of an options menu with a plurality of templates correspondingto different pre-selected portions of metadata to share.
 9. The methodof claim 8, wherein the selection of the portion of the metadatarelevant to the new recipient is received as a selection of one of thetemplates in the options menu.
 10. The method of claim 8, wherein one ofthe plurality of templates is a user-defined template.
 11. The method ofclaim 7, further comprising upon receiving the share action, causing adisplay of a suggested template corresponding to a pre-selected portionof metadata to share.
 12. The method of claim 11, wherein the selectionof the portion of the metadata relevant to the new recipient is receivedas a selection of the suggested template.
 13. The method of claim 7,wherein the shared message includes a message defined by the originalrecipient.
 14. The method of claim 7, wherein the shared messageincludes a forwarded copy of the email.
 15. The method of claim 7,wherein the shared message is an e-mail.
 16. A method for sharing eventswith structured metadata comprising: receiving a message transmittedfrom a sender to an original recipient that is related to an event forthe original recipient; identifying metadata of the event; creating acalendar item for the original recipient based on the metadata;receiving, from the original recipient, a share action identifying a newrecipient; receiving, from the original recipient, a selection of aportion of the metadata; receiving, from the original recipient, a shareaction identifying a new recipient; generating a shared message with theselected portion of the metadata; and transmitting the shared message tothe new recipient.
 17. The method of claim 16, wherein the sharedmessage includes a forwarded copy of the received message.
 18. Themethod of claim 16, further comprising causing a display of an optionsmenu with a plurality of templates corresponding to differentpre-selected portions of metadata to share.
 19. The method of claim 18,wherein the selection of the portion of the metadata relevant to the newrecipient is received as a selection of one of the templates in theoptions menu.
 20. The method of claim 16, further comprising uponreceiving the share action, causing a display of a suggested templatecorresponding to a pre-selected portion of metadata to share.